Copyright: Visual Help Copyright® 1993 Firas Bushnaq


CONTENTS
WinSwitch

WinSwitch is the utility that automates changing your Windows shell.  Select another shell from a user specified program list, instantly switch to the new shell and restart Windows with only a few clicks!

Table of Contents

Click on a topic to jump there:

Installation

Configuration

Operation

Troubleshooting

Notices

Developer

Freeware
Copyright (c) 1994 Roger C. Spaeder


Installation

The WinSwitch Files

•	WINSWTCH.EXE - The WinSwitch executable file

•	WINSWTCH.HLP - This WinSwitch help file

•	WINSWTCH.TXT - A text file containing information and installation instructions on WinSwitch

•	THREED.VBX - A support file needed for the three-dimensional  interface

Installing WinSwitch

•	THREED.VBX should be copied to your Windows system subdirectory.  All other files should be copied to a single directory or subdirectory reserved for the WinSwitch files, e.g., C:\UTILS\WINSWTCH.

•	In addition to the above files, you must have the Visual Basic 3.0 run-time module, VBRUN300.DLL, in your Windows system subdirectory.  The VBRUN300.DLL file is available from CompuServe and most BBSs.

•	WinSwitch is launched by running WINSWTCH.EXE.  After WinSwitch is loaded, a configuration file named WINSWTCH.INF will be created in the same directory.


Configuration

Introduction

     WinSwitch is a handy utility to automate changing your Windows shell.  From a user-specified list of shell programs, you can select a new shell, switch to it and restart Windows instantly.  WinSwitch makes the necessary alteration to the "shell" entry in the "[boot]" section of your SYSTEM.INI file without the need for tedious editing.  WinSwitch's button bar controls shell changing, configuration, restarting or exiting Windows, viewing current shell,getting on-line help, and closing WinSwitch.

Configuring WinSwitch

•	When WinSwitch is first loaded, it displays a list box with the user's initial shell shown first, along with several popular Windows shells.  The command line for each shell is displayed in the status panel below the list box.  As you click on a new shell selection, the command line for that selection appears.  A status panel at the bottom of WinSwitch explains the functions of the individual buttons and the list box.

•	To add or delete shell entries in the list box, click the configuration button on the button bar (wand icon).  A new window will appear that will enable you to enter or delete shell entries.

•	Before deleting an existing entry, you must first highlight that entry in the list box by clicking on it, and then click on the delete button twice -- once to set the delete operation and once to confirm it.

•	When adding a new shell entry, first type the title of the entry, for example, "Windows File Manager", in the title box.  Then enter the command line for the desired shell program in the command line box.  If the shell program is not on a directory in your system path, remember to include the direct path to the program in the command line, e.g., "C:\MIX\SHELL.EXE".  If the shell program is already on your path, you can enter the program name only, e.g., "PROGMAN.EXE", in the command line box.


Operation

Usage Tips for WinSwitch

•	Each time WinSwitch loads, it immediately displays the command line for the current shell program listed in the SYSTEM.INI file of your Windows directory.  At any time while using WinSwitch, you can check the identity of the current shell by clicking the view button (eye icon).

•	You should configure WinSwitch by adding your favorite shell programs.  Click the configure button (wand icon) and follow the instructions in the Configuration window of this help file.  Add the name and command line of your current shell, and then you can delete the entry for "User's Initial Shell".

•	Select a new shell by clicking once on its entry in the list box.  Switch to the new shell by double clicking on the entry or by clicking the switch button (arrows icon) on the button bar.  You will receive a confirmation prompt before making the actual change.

•	Once you have switched to a new Windows shell, you can activate the shell immediately by exiting and restarting Windows.  Click the exit/restart button (rocket icon) and then click either "Restart Windows" or "Exit Windows".  If you wish to immediately start a new Windows session after exiting, you should click restart.  Some of your running applications may prompt you for closing before the Windows exit is successful.  Simply close each application if requested, then click on the exit or restart menu item again.

•	WinSwitch always lists its shells in the order they are added to the list box.  If you wish to customize the order of the shell titles, delete all existing entries and then re-enter them in your preferred order.  WinSwitch will accept up to 50 different shell entries.


Troubleshooting

Problems and Solutions

•	When starting Windows, the message "Unable to locate PROGMAN.EXE" means that you have entered an incorrect or incomplete path and/or program name for your current shell.  You should use a DOS text editor like EDIT.COM to open the SYSTEM.INI file in your Windows directory and correct the entry, then restart Windows.  For example, if you enter the line "shell=progman.exe" in the "[boot]" section of your SYSTEM.INI file replacing the earlier "shell=XYZ.EXE" line, the Windows Program Manager will be set as the current shell.  Once Windows is running, you should launch WinSwitch and delete the incorrect list box entry, replacing it with the correct one.

•	The error message "Unable to find or load KRNL386.EXE" when starting Windows means that you must reboot before beginning another Windows session.  This error usually represents a SHARE.EXE violation arising from exiting a Windows application without closing it down normally, thereby leaving a system file logged as "open" by SHARE.EXE.  If you experience this message and don't wish to reboot each time you restart Windows, you should either close down all running applications before exiting Windows or eliminate SHARE.EXE from your environment.

File Protection

•	WinSwitch uses a standard Microsoft API call to change the shell entry in your SYSTEM.INI file.  As an extra precaution, when WinSwitch loads for the first time, it makes a backup copy of your existing SYSTEM.INI file, names it WINSWTCH.IN$ and places it in your Windows directory.  Should you ever need a duplicate of your original SYSTEM.INI file, you can always rename WINSWTCH.IN$.


Notices

Copyright

     WinSwitch was written with Microsoft's Visual Basic 3.0 Professional development system.

•	Copyright (c) 1994 Roger C. Spaeder, All Rights Reserved

License Rights

•	This software is licensed to you for no cost "as is" by the developer.  Licensor disclaims all warranties, either express or implied, including but not limited to implied warranties of merchantability, fitness for a particular purpose, and non-infringement, with respect to the software.

•	In no event will licensor be liable for damages, including any loss of profits, lost savings, lost time, replacement costs, technical assistance, computer hardware or software damage, personal injury, or any other incidental or consequential damages arising from your use or inability to use this software.  All rights under this limited non-exclusive license shall be determined in accordance with the laws of the State of Virginia.


Developer

WinSwitch

•	Developed by Roger C. Spaeder

•	CompuServe No. 73670,3161

•	7624 Georgetown Pike, McLean, Virginia 22102

•	Copyright (c) 1994 Roger C. Spaeder

Comments and Suggestions

WinSwitch is freeware.  Users with suggestions for improvements, questions, or bug reports  should contact the developer by mail or CompuServe at the addresses above.